@stefanocasazza This looks great!! Perhaps I should also update the new installation model to automatically save install logs, similar to what you have here

Keep an eye on #915 as a number of your variables, such as $DIR, can hopefully be replaced by framework-standard variables soon

Hi Hamilton,

Thanks for your appreciation and for your great work!

I wait for merging of #915
#915 to make the
update.

Greetings!

Stefano

2014-07-11 23:16 GMT+02:00 Hamilton Turner [email protected]:

@stefanocasazza https://github.com/stefanocasazza This looks great!!
Perhaps I should also update the new installation model to automatically
save install logs, similar to what you have here

Keep an eye on #915
#915 as a number
of your variables, such as $DIR, can hopefully be replaced by
framework-standard variables soon

—
Reply to this email directly or view it on GitHub
#921 (comment)
.

Hello Stefano,

PR 915 has just been merged, feel free to make whatever changes you deem necessary and I will get to them as soon as possible!

Hi Hamilton,

Thanks for the notification, I make the changes assuming that:

FWROOT=${HOME}/FrameworkBenchmarks
IROOT=${FWROOT}/ulib/installs

great work!

Stefano

2014-07-14 19:38 GMT+02:00 jyentechempower [email protected]:

Hello Stefano,

PR 915 has just been merged, feel free to make whatever changes you deem
necessary and I will get to them as soon as possible!

—
Reply to this email directly or view it on GitHub
#921 (comment)
.

Looks good, we should be pointing people to this file as an example of how to modify their own scripts.

PS - You may want to use TROOT instead of FWROOT in your install.sh, it lists the current directory of your test (e.g. $FWROOT/ULib for you), so you could reference your test files directly (e..g $TROOT/www) instead of hard-coding your benchmark's position in the git repo (e.g. if the folder structure of the repo changes, $FWROOT/ULib may no longer be the home of your test. If you're using TROOT, this change is invisible to you :-) )

PPS - sorry, I know this needs documentation...

ULib starts up a ton of userver_tcp instances, but doesn't seem to proceed beyond that. Does userver_tcp block? If so, you need to change this line to a non-blocking alternative.

Hi Alexander,

thanks for the advice, I made also various change for better understanding
of problem on installation, I hope for the best...

Stefano

Hello Stefano,

It appears that the install.sh for your framework is failing, output is here:

https://gist.github.com/jyentechempower/080021b82f8c5858d00a

Regards,

James

Hi @stefanocasazza. We finally have Round 10 preview data available. If you are available, could I solicit your opinion in the following thread at the Google Group?

https://groups.google.com/d/msg/framework-benchmarks/yyK8VclJ6Zc/Y4YRCWPUEJMJ

This is pertaining to the inclusion of a SQLite test which, upon further consideration, and in large part due to how it skews the results, I am considering hiding by default. Assuming you have a dissenting opinion--which would be completely understandable--I would like to have that captured so that we can factor that into our future planning.

Thank you!

Hi @bhauer,

first, I'd like to thank you and the team for the amazing work on these
benchmarks.
Regarding the inclusion of a SQLite choice, my vote would actually go for
hiding by default.
I also think it's better to differentiate to avoid how it skews the
results...

Congratulations again for the great job!

Stefano

2015-02-25 20:50 GMT+01:00 Brian Hauer [email protected]:

Hi @stefanocasazza https://github.com/stefanocasazza. We finally have
Round 10 preview data available. If you are available, could I solicit your
opinion in the following thread at the Google Group?

https://groups.google.com/d/msg/framework-benchmarks/yyK8VclJ6Zc/Y4YRCWPUEJMJ

This is pertaining to the inclusion of a SQLite test which, upon further
consideration, and in large part due to how it skews the results, I am
considering hiding by default. Assuming you have a dissenting
opinion--which would be completely understandable--I would like to have
that captured so that we can factor that into our future planning.

Thank you!

—
Reply to this email directly or view it on GitHub
#921 (comment)
.